Requirement Engineering Errors: Errors and Ambiguities of Visualization

Requirement Engineering encompasses the tasks that go into identifying, determining and understanding the customer needs as well as the expectations from the proposed software system or an application, taking account of possibly conflicting requirements of various stakeholders. Requirement Engineering, also referred to by names like requirement gathering or requirement analysis or requirement specification, is a well-defined stage in the software development life cycle. This stage is not only well defined but also very crucial to the success of software development. Most of the project failures have been attributed to this stage only. It's a general and very often heard statement: 'Requirements were not clear or Requirements were ambiguous'. So, what does this word 'Requirement' is all about, those requirement analysts try to establish and still, most of the projects fail due to lack of clarity in requirements. Requirements describe the behavior of the proposed software system but the roots of the same lie in the original real-time system for which software system has been proposed. Requirements engineering, in this manner, encompasses both the problem domain of the system as well as the solution domain of the system. The process of establishing the requirements is not an easy task as it is crossing over the boundaries of problem and the solution domain on a regular basis, and is bound to have errors. Errors in requirement engineering stage have many sources, ambiguous and unclear requirements are only a part of the problem. Having explored a number of common types of errors to find their source and strategies for dealing with them, Kurt Bittner [1] categorized requirement errors into three major